5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
- Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-4: Files and Fields

Files


The Files/Fields screen, shown below, displays when you select the files option from the Application Design menu. The Files/Fields screen presents a scrolling display of file specifications. Once specifications for a file have been entered, you can access the Fields screen for that file by selecting Enter .

Files/Fields Screen

The Files/Fields screen contains the following fields:

File Name uniquely identifies each file in a database. File Name also serves as the name of the current record area.

Description provides a longer, more flexibly formatted alternative to the technical File name. If blank, APPX uses the File name as the Description. Because Description is less cryptic and easier to understand than File Name, APPX uses it when communicating with users wherever possible. An example is the construction of error and warning messages. If a user selects an input process for a file that was not created (Balance, for example), the system might display the message 'Account Balance file does not exist.' We suggest that you use a plural entry for Description and avoid appending the word 'file'.

Organization determines the way records are stored in and retrieved from a file. The Org options are:

ONE-REC files are consecutive files that are limited to one record.

CONSEQ files are organized according to the relative sequence that records are added to a file. Records are retrieved by relative position.

INDEXED files are organized according to the content of specified fields, or key fields. Records are retrieved by key path.

The default is INDEXED. Refer to the File Organizationsection in for more information.

File Type There are two broad categories of file type: permanent and temporary. Permanent files are stored on disk and remain there whether the user is logged on or not. Temporary files can be available for a process and its subprocesses, for a set of related processes, or for an entire session. Temporary files can be stored on disk or in memory, or not stored at all. In general, memory files are faster and can improve performance. There are eight distinct file types:

PERMANENT files are stored on disk and remain there whether the user is logged on or not.

DISK-SUBPROCESS files are temporary, stored on disk, and deleted when the main process ends.

DISK-RELATED files are temporary, stored on disk, and deleted when the process that called the related processes (usually a job process) ends.

DISK-DETACHED files are temporary, stored on disk, and remain available until the user logs off.

MEMORY-SUBPROCESS files are temporary, stored in memory, and deleted when the main process ends.

MEMORY-RELATED files are temporary, stored in memory, and deleted when the process that called the related processes (usually a job process) ends.

MEMORY-DETACHED files are temporary, stored in memory, and remain available until the user logs off.

WORKING-STORAGE files are temporary, not stored at all, and deleted when the process that is using them ends. For instance, working-storage files can be used to pass file-related information from an update process to a related subroutine. Refer to the Working-Storage Files section in this manual for more information.

Interprocess Communication provides a complete discussion of detached, related, and subprocess files and processes. Also, refer to the File Storage Options and Temporary versus Permanent Files sections of this manual for additional information.

Options are indicators that are present whenever documentation (T), rules (R), additional attributes (AA), record protection (RP), or default process (DP) have been defined for this file.

The Files/Fields screen contains the following options as described in the corresponding sections:

Additional Attributes

Rules

Record Protection

Default Process

Documentation

Security

Application Design Manual                                         "Powered by Appx Software"

1004

©2006 By APPX Software, Inc. All Rights Reserved